Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dfd2d07e2013f49907b0eb4937336cf8205f7455ad843657933dcc4542d728c

Tx prefix hash: df722e464ce7d8f7af2bc8512bf9008894191935b1004bc256e0407d50506b9f
Tx public key: 61d4f643f8cba949b6d6be2a4eb0d0ae65216fcf971080d70c08551743c4a0e9
Timestamp: 1625051529 Timestamp [UCT]: 2021-06-30 11:12:09 Age [y:d:h:m:s]: 03:337:13:17:21
Block: 285864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1010128 RingCT/type: yes/0
Extra: 0161d4f643f8cba949b6d6be2a4eb0d0ae65216fcf971080d70c08551743c4a0e90211000002bdb8178fc1000000000000000000

1 output(s) for total of 69.312954477000 dcy

stealth address amount amount idx
00: b0c238b670974b7edd983aa6b3b56a7635d76dfbcbd6ecf9ff19a0734edc6ae5 69.312954477000 598667 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": 285874, "vin": [ { "gen": { "height": 285864 } } ], "vout": [ { "amount": 69312954477, "target": { "key": "b0c238b670974b7edd983aa6b3b56a7635d76dfbcbd6ecf9ff19a0734edc6ae5" } } ], "extra": [ 1, 97, 212, 246, 67, 248, 203, 169, 73, 182, 214, 190, 42, 78, 176, 208, 174, 101, 33, 111, 207, 151, 16, 128, 215, 12, 8, 85, 23, 67, 196, 160, 233, 2, 17, 0, 0, 2, 189, 184, 23, 143, 193, 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