Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18a2b7c7a9939f2f36117470f053f93dd12303a1fb3121df5e96c55706dfb659

Tx prefix hash: 34b4a7cc536fbc7a47eb9080a03c2f20598f1db5bf4867ce8da67050529b83b1
Tx public key: 157d2394c4efce9fd1050d4b1357b296f01572fbdf13efd8799c0f8f3cefdd38
Timestamp: 1726938507 Timestamp [UCT]: 2024-09-21 17:08:27 Age [y:d:h:m:s]: 00:216:19:45:10
Block: 1115077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154804 RingCT/type: yes/0
Extra: 01157d2394c4efce9fd1050d4b1357b296f01572fbdf13efd8799c0f8f3cefdd3802110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b514d0a59bd736d2ed29d66f3b90a4514ff08391a72371636a2cb5736de103d0 0.600000000000 1595084 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": 1115087, "vin": [ { "gen": { "height": 1115077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b514d0a59bd736d2ed29d66f3b90a4514ff08391a72371636a2cb5736de103d0" } } ], "extra": [ 1, 21, 125, 35, 148, 196, 239, 206, 159, 209, 5, 13, 75, 19, 87, 178, 150, 240, 21, 114, 251, 223, 19, 239, 216, 121, 156, 15, 143, 60, 239, 221, 56, 2, 17, 0, 0, 0, 11, 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