Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2d5edf99cc99acfc50adfee45aeeb8735a0d68b67de656c900e19040c03b787

Tx prefix hash: 0afabb439bdb719342dce156a15aebe8729205963c8e628c8d1890457292ea68
Tx public key: 856bb0d58837aaa54521cce7b8d0f94990aa083c67d9726cf1df0d02c89a5864
Timestamp: 1697871935 Timestamp [UCT]: 2023-10-21 07:05:35 Age [y:d:h:m:s]: 01:172:20:10:01
Block: 874302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384561 RingCT/type: yes/0
Extra: 01856bb0d58837aaa54521cce7b8d0f94990aa083c67d9726cf1df0d02c89a5864021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.778170127000 dcy

stealth address amount amount idx
00: 3422c714c8ef315f023e4c3abd5823f2c061d3666953974e7bd99c06c64c8a74 0.778170127000 1329508 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": 874312, "vin": [ { "gen": { "height": 874302 } } ], "vout": [ { "amount": 778170127, "target": { "key": "3422c714c8ef315f023e4c3abd5823f2c061d3666953974e7bd99c06c64c8a74" } } ], "extra": [ 1, 133, 107, 176, 213, 136, 55, 170, 165, 69, 33, 204, 231, 184, 208, 249, 73, 144, 170, 8, 60, 103, 217, 114, 108, 241, 223, 13, 2, 200, 154, 88, 100, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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