Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be73b4159118906c9ae0f92bef88e83df5ddec4c828e743cc4c75c4e40169d8e

Tx prefix hash: 7fbee6300b36ab2b1536476101c512ae3fa24eaed9a7d3d76fc00675729463e9
Tx public key: 4f5707c83c3cfd17144d23ee42f51454f996857b0183bc1f60e15c1eb9648fd4
Timestamp: 1708777201 Timestamp [UCT]: 2024-02-24 12:20:01 Age [y:d:h:m:s]: 01:284:23:33:00
Block: 964515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462456 RingCT/type: yes/0
Extra: 014f5707c83c3cfd17144d23ee42f51454f996857b0183bc1f60e15c1eb9648fd402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7b14dbdda01f93e2162bf7f4e7596e229ad392206a6d6a4e7f176ea69d2669c 0.600000000000 1424256 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": 964525, "vin": [ { "gen": { "height": 964515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7b14dbdda01f93e2162bf7f4e7596e229ad392206a6d6a4e7f176ea69d2669c" } } ], "extra": [ 1, 79, 87, 7, 200, 60, 60, 253, 23, 20, 77, 35, 238, 66, 245, 20, 84, 249, 150, 133, 123, 1, 131, 188, 31, 96, 225, 92, 30, 185, 100, 143, 212, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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