Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: decfb9dd3a5e1dfc3d7c6567e37fb574e46ba8f093d2e8343afe8236e9632d4c

Tx prefix hash: 1b6710b1f8aa248270947dac607511c622c079b16ac86995b58798b2b5730c28
Tx public key: e78e97d25d37d6e54496714585b65d27f1dffcf98b41431ef9d60963d3afd52a
Timestamp: 1737343191 Timestamp [UCT]: 2025-01-20 03:19:51 Age [y:d:h:m:s]: 00:300:22:04:55
Block: 1201145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212609 RingCT/type: yes/0
Extra: 01e78e97d25d37d6e54496714585b65d27f1dffcf98b41431ef9d60963d3afd52a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1795e1574c123fde58af94b8af457a345ce04027faf8a4a76ae8d4b8dc0e95a 0.600000000000 1687794 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": 1201155, "vin": [ { "gen": { "height": 1201145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1795e1574c123fde58af94b8af457a345ce04027faf8a4a76ae8d4b8dc0e95a" } } ], "extra": [ 1, 231, 142, 151, 210, 93, 55, 214, 229, 68, 150, 113, 69, 133, 182, 93, 39, 241, 223, 252, 249, 139, 65, 67, 30, 249, 214, 9, 99, 211, 175, 213, 42, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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