Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8a7220d82c7cf34fc15bfc13c5a92a8472dbc8e701925bebdedb154d75f3830

Tx prefix hash: 76b2b4a1786d64e8d516a1c719b6c19e83835aef234bdb8503406717d3a2974a
Tx public key: ba09c41d40cb952578d7e5f3fa23709110810c28af6fe48ac0b39d101913f425
Timestamp: 1717599395 Timestamp [UCT]: 2024-06-05 14:56:35 Age [y:d:h:m:s]: 01:158:04:49:07
Block: 1037657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371641 RingCT/type: yes/0
Extra: 01ba09c41d40cb952578d7e5f3fa23709110810c28af6fe48ac0b39d101913f42502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5872a4b302dcb8bb78e56f75c7a31774ba5501838c7ad01b812ef90f2563807 0.600000000000 1506210 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": 1037667, "vin": [ { "gen": { "height": 1037657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5872a4b302dcb8bb78e56f75c7a31774ba5501838c7ad01b812ef90f2563807" } } ], "extra": [ 1, 186, 9, 196, 29, 64, 203, 149, 37, 120, 215, 229, 243, 250, 35, 112, 145, 16, 129, 12, 40, 175, 111, 228, 138, 192, 179, 157, 16, 25, 19, 244, 37, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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