Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bcf336613308017cd7a7c9dc390af08692399f385812d65079b3c56ad45d1b7

Tx prefix hash: 5c3424c3a1a545505290caaf84c930c01d52fd4d7eecd53262f36d7925e5c106
Tx public key: 6bf9bb34a3d1cb32621a6cb05098851e7af4f04d98453319d6360af1e5317391
Timestamp: 1715054289 Timestamp [UCT]: 2024-05-07 03:58:09 Age [y:d:h:m:s]: 00:331:22:46:38
Block: 1016559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237262 RingCT/type: yes/0
Extra: 016bf9bb34a3d1cb32621a6cb05098851e7af4f04d98453319d6360af1e53173910211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aaa5ceed53b5f1680fc8e17470ba2503461b870ca8f11d38043a6e646b946e5 0.600000000000 1480176 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": 1016569, "vin": [ { "gen": { "height": 1016559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aaa5ceed53b5f1680fc8e17470ba2503461b870ca8f11d38043a6e646b946e5" } } ], "extra": [ 1, 107, 249, 187, 52, 163, 209, 203, 50, 98, 26, 108, 176, 80, 152, 133, 30, 122, 244, 240, 77, 152, 69, 51, 25, 214, 54, 10, 241, 229, 49, 115, 145, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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