Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5251eeda40917f9ccb6537221b62df58e6aa0c774e20ee4b31b1ee688484e7a1

Tx prefix hash: 69086c0da9e8b12fb7bd734e21774847f89553cf641f9dacb2db005ae899f22e
Tx public key: 427395030cb0bb19fb7cb3b53083ee12804b14330f0e05a9237c10fedfa0b070
Timestamp: 1710930334 Timestamp [UCT]: 2024-03-20 10:25:34 Age [y:d:h:m:s]: 01:007:15:06:16
Block: 982389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266401 RingCT/type: yes/0
Extra: 01427395030cb0bb19fb7cb3b53083ee12804b14330f0e05a9237c10fedfa0b07002110000000279bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ae4a9c544a327af551e56c766d83c75e0da3e91347d3b081f9b4b7d148a759e 0.600000000000 1442494 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": 982399, "vin": [ { "gen": { "height": 982389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ae4a9c544a327af551e56c766d83c75e0da3e91347d3b081f9b4b7d148a759e" } } ], "extra": [ 1, 66, 115, 149, 3, 12, 176, 187, 25, 251, 124, 179, 181, 48, 131, 238, 18, 128, 75, 20, 51, 15, 14, 5, 169, 35, 124, 16, 254, 223, 160, 176, 112, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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