Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b16254925fac96fb1304da91a21f3e49ce19abfad0b2c4d2ddb5d57679192878

Tx prefix hash: b41312b717a3fb2798a86814858f4ae8aa16f50e5918a6c234f20fd5cbfc9d5d
Tx public key: 327f3ebe23ef159501be3b251cf683f7b9f04b9f8a3169e2ff596ce08ec2afd1
Timestamp: 1724621038 Timestamp [UCT]: 2024-08-25 21:23:58 Age [y:d:h:m:s]: 01:087:19:54:49
Block: 1095861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321229 RingCT/type: yes/0
Extra: 01327f3ebe23ef159501be3b251cf683f7b9f04b9f8a3169e2ff596ce08ec2afd102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b734baef073a6bb1f7cafa79605d15e48b0a8d432d2f29cf72e9e79d90403d09 0.600000000000 1571044 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": 1095871, "vin": [ { "gen": { "height": 1095861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b734baef073a6bb1f7cafa79605d15e48b0a8d432d2f29cf72e9e79d90403d09" } } ], "extra": [ 1, 50, 127, 62, 190, 35, 239, 21, 149, 1, 190, 59, 37, 28, 246, 131, 247, 185, 240, 75, 159, 138, 49, 105, 226, 255, 89, 108, 224, 142, 194, 175, 209, 2, 17, 0, 0, 0, 2, 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