Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd4dbe4290902f0d300701abb3ebcef08b7fa44fb8d8232542adc9b0a14d11fd

Tx prefix hash: cb91b8823789674abf3fac8c2d6679923abe69f275a74ead2c484541a1f9acf8
Tx public key: 6a68d8c330595648770df4e4d949160a6782189d0490f1a7a68feb50ae25372a
Timestamp: 1581292691 Timestamp [UCT]: 2020-02-09 23:58:11 Age [y:d:h:m:s]: 05:024:11:33:16
Block: 61713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170208 RingCT/type: yes/0
Extra: 016a68d8c330595648770df4e4d949160a6782189d0490f1a7a68feb50ae25372a0211000000014943cd9f000000000000000000

1 output(s) for total of 383.291726030000 dcy

stealth address amount amount idx
00: b28118bf3111f278e28be1a87c7319cd94a7ca1095f279dd012929c8d5626571 383.291726030000 113789 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": 61723, "vin": [ { "gen": { "height": 61713 } } ], "vout": [ { "amount": 383291726030, "target": { "key": "b28118bf3111f278e28be1a87c7319cd94a7ca1095f279dd012929c8d5626571" } } ], "extra": [ 1, 106, 104, 216, 195, 48, 89, 86, 72, 119, 13, 244, 228, 217, 73, 22, 10, 103, 130, 24, 157, 4, 144, 241, 167, 166, 143, 235, 80, 174, 37, 55, 42, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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