Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 644f5b42506dbdc330ef9a70fbac6fef3d701e8090d39cfabe7076d79feb70cf

Tx prefix hash: 2ceb9d8f0de5704d0e7e331c683587c86777862bc5e1b717868aa9a4b847c8b9
Tx public key: 2e2f7f2da3f90ac199f7f636c6e0160942301ae64ef175aae2d13b1701867976
Timestamp: 1703021508 Timestamp [UCT]: 2023-12-19 21:31:48 Age [y:d:h:m:s]: 01:118:13:36:28
Block: 916804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345867 RingCT/type: yes/0
Extra: 012e2f7f2da3f90ac199f7f636c6e0160942301ae64ef175aae2d13b1701867976021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be1e8762675604e288296dbcb31b9dd3b70189b79ac7d963976a261ee11415f0 0.600000000000 1374364 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": 916814, "vin": [ { "gen": { "height": 916804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be1e8762675604e288296dbcb31b9dd3b70189b79ac7d963976a261ee11415f0" } } ], "extra": [ 1, 46, 47, 127, 45, 163, 249, 10, 193, 153, 247, 246, 54, 198, 224, 22, 9, 66, 48, 26, 230, 78, 241, 117, 170, 226, 209, 59, 23, 1, 134, 121, 118, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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