Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1e494e9fe82f85204f3ba3f7f2c870c76dcda659aeb87bcae14b67bcec51652

Tx prefix hash: edd7b73415d08c3fc3e9fc63458b7ab06b050d1ef139eb16326ed29dd7eda48d
Tx public key: a1d188e511f11ee138d05e3fa0a8b12477d4f6ef8b92d94affc7a0529de264e9
Timestamp: 1627838913 Timestamp [UCT]: 2021-08-01 17:28:33 Age [y:d:h:m:s]: 03:287:02:25:27
Block: 305323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 977642 RingCT/type: yes/0
Extra: 01a1d188e511f11ee138d05e3fa0a8b12477d4f6ef8b92d94affc7a0529de264e902110000002be084ab86000000000000000000

1 output(s) for total of 59.750100222000 dcy

stealth address amount amount idx
00: c3a55af22970a7ed74a3d9cebbc2e0d5861878826298012b1ff57fd720d5295f 59.750100222000 636906 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": 305333, "vin": [ { "gen": { "height": 305323 } } ], "vout": [ { "amount": 59750100222, "target": { "key": "c3a55af22970a7ed74a3d9cebbc2e0d5861878826298012b1ff57fd720d5295f" } } ], "extra": [ 1, 161, 209, 136, 229, 17, 241, 30, 225, 56, 208, 94, 63, 160, 168, 177, 36, 119, 212, 246, 239, 139, 146, 217, 74, 255, 199, 160, 82, 157, 226, 100, 233, 2, 17, 0, 0, 0, 43, 224, 132, 171, 134, 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