Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3f591164334ee5cc9fcfb29ad8b2fe2461606eeb1f218502fd9ee7e12a3b154

Tx prefix hash: d539935df7a4a7df72398cf9a253c498290a9cb52d1f4cfd320b87d89063ec93
Tx public key: 45b7832f2bf5c58a049dc49f5fcddd3b077fd11e31ad9b6142251403c20aca3a
Timestamp: 1762046477 Timestamp [UCT]: 2025-11-02 01:21:17 Age [y:d:h:m:s]: 00:007:20:43:10
Block: 1403019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5638 RingCT/type: yes/0
Extra: 0145b7832f2bf5c58a049dc49f5fcddd3b077fd11e31ad9b6142251403c20aca3a0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79390c0d30cb67842dd9c9cd639349cbc11470fcac9890aafad22a263b6f14f0 0.600000000000 1891346 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": 1403029, "vin": [ { "gen": { "height": 1403019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79390c0d30cb67842dd9c9cd639349cbc11470fcac9890aafad22a263b6f14f0" } } ], "extra": [ 1, 69, 183, 131, 47, 43, 245, 197, 138, 4, 157, 196, 159, 95, 205, 221, 59, 7, 127, 209, 30, 49, 173, 155, 97, 66, 37, 20, 3, 194, 10, 202, 58, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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