Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6505115eb9c13fac502e91148109da37a0529fa59ccb8a41f1828d0804b5658e

Tx prefix hash: 8c1e361e09ee4711001c05849445094b99445ba540d682003a5a0d7894084462
Tx public key: a54d44fdc5b631fcde885b532ab0a475cb97a5de0fee4c631f5d976b7d779eed
Timestamp: 1702222688 Timestamp [UCT]: 2023-12-10 15:38:08 Age [y:d:h:m:s]: 01:122:10:20:59
Block: 910167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348649 RingCT/type: yes/0
Extra: 01a54d44fdc5b631fcde885b532ab0a475cb97a5de0fee4c631f5d976b7d779eed02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a82e26201f899a9ec289877a098fba4fb6d3e4823b970084ac54bdd8b740606 0.600000000000 1367312 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": 910177, "vin": [ { "gen": { "height": 910167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a82e26201f899a9ec289877a098fba4fb6d3e4823b970084ac54bdd8b740606" } } ], "extra": [ 1, 165, 77, 68, 253, 197, 182, 49, 252, 222, 136, 91, 83, 42, 176, 164, 117, 203, 151, 165, 222, 15, 238, 76, 99, 31, 93, 151, 107, 125, 119, 158, 237, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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