Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91de81bcb01a1a25a486762df9f79e22a4485a43bb2d0dd3786d2c3cea31698e

Tx prefix hash: 0ff3290775cdba3817bc631cf079d900a42994da6ff1d2de7bf8ab30b5c2d489
Tx public key: 5e2cc3a99bf8ed6c1fd383686f1c54b3477bf95da3d02910f93f086b07eacf55
Timestamp: 1751423584 Timestamp [UCT]: 2025-07-02 02:33:04 Age [y:d:h:m:s]: 00:175:00:59:24
Block: 1316940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123370 RingCT/type: yes/0
Extra: 015e2cc3a99bf8ed6c1fd383686f1c54b3477bf95da3d02910f93f086b07eacf5502110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e5a618951fdbce8a29c1e89a3f8656b5ef819595f52efa098c9dee99dcd72bd 0.600000000000 1804605 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": 1316950, "vin": [ { "gen": { "height": 1316940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e5a618951fdbce8a29c1e89a3f8656b5ef819595f52efa098c9dee99dcd72bd" } } ], "extra": [ 1, 94, 44, 195, 169, 155, 248, 237, 108, 31, 211, 131, 104, 111, 28, 84, 179, 71, 123, 249, 93, 163, 208, 41, 16, 249, 63, 8, 107, 7, 234, 207, 85, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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