Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2a2adf27cd904726090523b5711d90658e8a5f0fbda0cbcbd1ee8608a90f78c

Tx prefix hash: faa5e26ce8ab0f11d1599c28dc22606dc072826581c5f200efcc76420ac39322
Tx public key: 2507de8831d15f8e606cb88e3543a8b0ba3b65b2b07c66c474e3d6fd3708bb8c
Timestamp: 1721246138 Timestamp [UCT]: 2024-07-17 19:55:38 Age [y:d:h:m:s]: 00:305:04:01:16
Block: 1067893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218036 RingCT/type: yes/0
Extra: 012507de8831d15f8e606cb88e3543a8b0ba3b65b2b07c66c474e3d6fd3708bb8c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 171affc5b153cb7dfa5214c11157d3f10333a6fc98865142e0c6b8f3be6ec218 0.600000000000 1538834 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": 1067903, "vin": [ { "gen": { "height": 1067893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "171affc5b153cb7dfa5214c11157d3f10333a6fc98865142e0c6b8f3be6ec218" } } ], "extra": [ 1, 37, 7, 222, 136, 49, 209, 95, 142, 96, 108, 184, 142, 53, 67, 168, 176, 186, 59, 101, 178, 176, 124, 102, 196, 116, 227, 214, 253, 55, 8, 187, 140, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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