Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1474fcbadbc35ac94655c8bb43f2c87d3ba34972a74a74fc2f5c83dc895b10d

Tx prefix hash: bf298d6fb0efb5f7fd2598d4022c384fc16ab0fbdcc04040a3d79e9844f735dc
Tx public key: 70ed15bc790d80b4330612bb6e287126d2ca7d885c2d475347101235b8d556ae
Timestamp: 1695929455 Timestamp [UCT]: 2023-09-28 19:30:55 Age [y:d:h:m:s]: 01:200:12:16:48
Block: 858206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404353 RingCT/type: yes/0
Extra: 0170ed15bc790d80b4330612bb6e287126d2ca7d885c2d475347101235b8d556ae02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.879847305000 dcy

stealth address amount amount idx
00: 2fb471300bb69ed09941e0c618b82ffc9c957c71c13e0e6fcd34a04ad7ce45a7 0.879847305000 1312372 of 0

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": 858216, "vin": [ { "gen": { "height": 858206 } } ], "vout": [ { "amount": 879847305, "target": { "key": "2fb471300bb69ed09941e0c618b82ffc9c957c71c13e0e6fcd34a04ad7ce45a7" } } ], "extra": [ 1, 112, 237, 21, 188, 121, 13, 128, 180, 51, 6, 18, 187, 110, 40, 113, 38, 210, 202, 125, 136, 92, 45, 71, 83, 71, 16, 18, 53, 184, 213, 86, 174, 2, 17, 0, 0, 0, 6, 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