Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6fb73bebff5d83ecb2144370a3db6ba8d808684a3d069a4764eb0004d2e46c6

Tx prefix hash: 2ac6b547da4a477250ce209ad0c68532e47bb2bf11c1eba11dbe785199178a30
Tx public key: e1a83560d4c2e789bd92f530bafb0dce63d801c9a14d27934b9bb0a4abb41d6a
Timestamp: 1737826724 Timestamp [UCT]: 2025-01-25 17:38:44 Age [y:d:h:m:s]: 00:142:20:48:28
Block: 1205158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101851 RingCT/type: yes/0
Extra: 01e1a83560d4c2e789bd92f530bafb0dce63d801c9a14d27934b9bb0a4abb41d6a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00add18773ddb3f7291d90973b8856b58502d88023cfdc96bb74654676d59632 0.600000000000 1691855 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": 1205168, "vin": [ { "gen": { "height": 1205158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00add18773ddb3f7291d90973b8856b58502d88023cfdc96bb74654676d59632" } } ], "extra": [ 1, 225, 168, 53, 96, 212, 194, 231, 137, 189, 146, 245, 48, 186, 251, 13, 206, 99, 216, 1, 201, 161, 77, 39, 147, 75, 155, 176, 164, 171, 180, 29, 106, 2, 17, 0, 0, 0, 4, 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