Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d8cbd2ab2064c04d62edf98f4df5b0503b1f75827aa54a0c97c4b524e00f4ee0

Tx prefix hash: b7f06cd42783df62939dd7c13396044d67debdc77d854b3a816f7d895696db5f
Tx public key: b7c37a2c6d92684908223d73d408f798fd669788c5b12c5676fdb3446d5584cf
Timestamp: 1761916714 Timestamp [UCT]: 2025-10-31 13:18:34 Age [y:d:h:m:s]: 00:006:12:24:55
Block: 1401954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4648 RingCT/type: yes/0
Extra: 01b7c37a2c6d92684908223d73d408f798fd669788c5b12c5676fdb3446d5584cf02110000001525a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15779b3101fa1d2e182e02d6fc2e048f73a2ce373c4e98ffcccc1bc6b80fa577 0.600000000000 1890273 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1401964, "vin": [ { "gen": { "height": 1401954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15779b3101fa1d2e182e02d6fc2e048f73a2ce373c4e98ffcccc1bc6b80fa577" } } ], "extra": [ 1, 183, 195, 122, 44, 109, 146, 104, 73, 8, 34, 61, 115, 212, 8, 247, 152, 253, 102, 151, 136, 197, 177, 44, 86, 118, 253, 179, 68, 109, 85, 132, 207, 2, 17, 0, 0, 0, 21, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8