Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87ca39cf8cbd5ce6ebc002b372a6bf02825a5898e6321a4ec7e75c63014600e1

Tx prefix hash: 752adf59c526a9f99407d0a73de5d2cdc8245b43cf45f137e0b8c233493b9e5a
Tx public key: 240101ebd68fea809777ccf2da55e1218fa0db26677d256c8d544ef5fcf34ef4
Timestamp: 1583238496 Timestamp [UCT]: 2020-03-03 12:28:16 Age [y:d:h:m:s]: 04:078:08:33:54
Block: 75608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 950050 RingCT/type: yes/0
Extra: 01240101ebd68fea809777ccf2da55e1218fa0db26677d256c8d544ef5fcf34ef402110000007dc71d3ff9000000000000000000

1 output(s) for total of 344.730814917000 dcy

stealth address amount amount idx
00: 0a4dbfc48b83fe245ce92b00933a6f0cf3309c9f6953e8be7c7219d4704bb7f4 344.730814917000 139562 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": 75618, "vin": [ { "gen": { "height": 75608 } } ], "vout": [ { "amount": 344730814917, "target": { "key": "0a4dbfc48b83fe245ce92b00933a6f0cf3309c9f6953e8be7c7219d4704bb7f4" } } ], "extra": [ 1, 36, 1, 1, 235, 214, 143, 234, 128, 151, 119, 204, 242, 218, 85, 225, 33, 143, 160, 219, 38, 103, 125, 37, 108, 141, 84, 78, 245, 252, 243, 78, 244, 2, 17, 0, 0, 0, 125, 199, 29, 63, 249, 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