Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4452b2296f6d0bf80d0d6839fe142e1ed525fc0389c65fb017d9d04c5facaa41

Tx prefix hash: 3a42796a56c5665ea34919c848261a928214102bb5de1aec2e09b6ebc2026615
Tx public key: 719dd058bbc8f8a1163d0d2a46836078bf1c23926c78a909ec8a6af897e7ad6d
Timestamp: 1715448627 Timestamp [UCT]: 2024-05-11 17:30:27 Age [y:d:h:m:s]: 00:183:11:18:04
Block: 1019852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131295 RingCT/type: yes/0
Extra: 01719dd058bbc8f8a1163d0d2a46836078bf1c23926c78a909ec8a6af897e7ad6d02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e87017e5e97f7c4121cb8e158bf3481c1ec1f16c1163a8f6b1f18e2d9feab7 0.600000000000 1483905 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": 1019862, "vin": [ { "gen": { "height": 1019852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e87017e5e97f7c4121cb8e158bf3481c1ec1f16c1163a8f6b1f18e2d9feab7" } } ], "extra": [ 1, 113, 157, 208, 88, 187, 200, 248, 161, 22, 61, 13, 42, 70, 131, 96, 120, 191, 28, 35, 146, 108, 120, 169, 9, 236, 138, 106, 248, 151, 231, 173, 109, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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