Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c70bd2d5ac37858b62a63521478c928ecfe88be879b2d9142f2062e8c95e404d

Tx prefix hash: 11a9f0507c6f3e743ad0fa683811ba8b4bc34ec87cc40344e72bc90b098b9e78
Tx public key: 3661caaa9b38e4571df1ddcbb5a9c87da61fed013bd898163908b81bc0ce2cb6
Timestamp: 1578318911 Timestamp [UCT]: 2020-01-06 13:55:11 Age [y:d:h:m:s]: 04:355:01:12:10
Block: 39709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143240 RingCT/type: yes/0
Extra: 013661caaa9b38e4571df1ddcbb5a9c87da61fed013bd898163908b81bc0ce2cb602110000000117786bcf000000000000000000

1 output(s) for total of 453.344600061000 dcy

stealth address amount amount idx
00: af6c786b3123ddaa6bf0e1235bf832b60e41c20bf9dcc551340d1c2abb405961 453.344600061000 68893 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": 39719, "vin": [ { "gen": { "height": 39709 } } ], "vout": [ { "amount": 453344600061, "target": { "key": "af6c786b3123ddaa6bf0e1235bf832b60e41c20bf9dcc551340d1c2abb405961" } } ], "extra": [ 1, 54, 97, 202, 170, 155, 56, 228, 87, 29, 241, 221, 203, 181, 169, 200, 125, 166, 31, 237, 1, 59, 216, 152, 22, 57, 8, 184, 27, 192, 206, 44, 182, 2, 17, 0, 0, 0, 1, 23, 120, 107, 207, 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