Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 029142987fd690036dc944a2deca3b57f0e292b356d0b62f866628e96810f5bb

Tx prefix hash: 1829f59caada2b0ca0949c03ee1a30d9d2322e66fc16061fdec44d6e25d0ac72
Tx public key: d0cca3fa2faef691938d74072d2ac3dfa914c4a1cf95fc715de183ea87ce668f
Timestamp: 1696391364 Timestamp [UCT]: 2023-10-04 03:49:24 Age [y:d:h:m:s]: 01:254:18:59:28
Block: 862019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443117 RingCT/type: yes/0
Extra: 01d0cca3fa2faef691938d74072d2ac3dfa914c4a1cf95fc715de183ea87ce668f02110000000233af99f4000000000000000000

1 output(s) for total of 0.854620391000 dcy

stealth address amount amount idx
00: b5d618f64c08a4bb5f9d6de580510140903c75ec9dce8d8937cefb24dbc0eee9 0.854620391000 1316399 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": 862029, "vin": [ { "gen": { "height": 862019 } } ], "vout": [ { "amount": 854620391, "target": { "key": "b5d618f64c08a4bb5f9d6de580510140903c75ec9dce8d8937cefb24dbc0eee9" } } ], "extra": [ 1, 208, 204, 163, 250, 47, 174, 246, 145, 147, 141, 116, 7, 45, 42, 195, 223, 169, 20, 196, 161, 207, 149, 252, 113, 93, 225, 131, 234, 135, 206, 102, 143, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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