Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e830b5f36908f977b964ec17aa14edafa796bca08a34a57e05499d15eafbdf

Tx prefix hash: f1f3f981070ea69aac17a07c90080afd331e9a2a5e23d5da2ad489ccdd347031
Tx public key: b0ddb8ab0672608e6a592690e8b8e2e7f832a61b7501ce51b01037069e365967
Timestamp: 1636738598 Timestamp [UCT]: 2021-11-12 17:36:38 Age [y:d:h:m:s]: 03:122:22:16:54
Block: 372953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 866277 RingCT/type: yes/0
Extra: 01b0ddb8ab0672608e6a592690e8b8e2e7f832a61b7501ce51b01037069e36596702110000000606faf294000000000000000000

1 output(s) for total of 35.667225534000 dcy

stealth address amount amount idx
00: 43ead94b102324275bdf4caead1c1a2730b73fb9c03c981aa521c19e5f59fc43 35.667225534000 755351 of 0

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": 372963, "vin": [ { "gen": { "height": 372953 } } ], "vout": [ { "amount": 35667225534, "target": { "key": "43ead94b102324275bdf4caead1c1a2730b73fb9c03c981aa521c19e5f59fc43" } } ], "extra": [ 1, 176, 221, 184, 171, 6, 114, 96, 142, 106, 89, 38, 144, 232, 184, 226, 231, 248, 50, 166, 27, 117, 1, 206, 81, 176, 16, 55, 6, 158, 54, 89, 103, 2, 17, 0, 0, 0, 6, 6, 250, 242, 148, 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