Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73761e9f4c8926c9ff3b6e54050ef9139a24f5944f3676d90f18143f3b01e5f6

Tx prefix hash: 935e39fc80b7004e61e1ac62f16610501eb3250ceb47158409f52490c0ba34df
Tx public key: 61dcf37cd2d64cfe712cc69350c0de63d1487ad5e7c19cc3c47e3b0bf770b04a
Timestamp: 1727739159 Timestamp [UCT]: 2024-09-30 23:32:39 Age [y:d:h:m:s]: 00:054:08:03:29
Block: 1121722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38819 RingCT/type: yes/0
Extra: 0161dcf37cd2d64cfe712cc69350c0de63d1487ad5e7c19cc3c47e3b0bf770b04a021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e314b66face640d008451da3b22525da0e3db049b336668d1ed7704b9d14c6d3 0.600000000000 1604047 of 15

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": 1121732, "vin": [ { "gen": { "height": 1121722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e314b66face640d008451da3b22525da0e3db049b336668d1ed7704b9d14c6d3" } } ], "extra": [ 1, 97, 220, 243, 124, 210, 214, 76, 254, 113, 44, 198, 147, 80, 192, 222, 99, 209, 72, 122, 213, 231, 193, 156, 195, 196, 126, 59, 11, 247, 112, 176, 74, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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