Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1896a3ae53e2734f4cad32be16e1c22d2ee6ffe407dee670c7fb7cf534405799

Tx prefix hash: 81386d6eb94e390eaca9f648606b4345375b24ecb3b48999810f484ff9cc3db6
Tx public key: 5533377008d513f8097f8185c3c613a692d0970d1f2f74e373e582a1aa4f5f8d
Timestamp: 1750660333 Timestamp [UCT]: 2025-06-23 06:32:13 Age [y:d:h:m:s]: 00:149:07:36:20
Block: 1310966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104604 RingCT/type: yes/0
Extra: 015533377008d513f8097f8185c3c613a692d0970d1f2f74e373e582a1aa4f5f8d0211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9075f8bce8a4b31f0bcf58eec5882b7409e87734e9949f1e13bbb8cc26281ae 0.600000000000 1798589 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": 1310976, "vin": [ { "gen": { "height": 1310966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9075f8bce8a4b31f0bcf58eec5882b7409e87734e9949f1e13bbb8cc26281ae" } } ], "extra": [ 1, 85, 51, 55, 112, 8, 213, 19, 248, 9, 127, 129, 133, 195, 198, 19, 166, 146, 208, 151, 13, 31, 47, 116, 227, 115, 229, 130, 161, 170, 79, 95, 141, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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