Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44f62be5fb82687f5a3fc8ce725648aea2dfc4acdc61858b3775cb2e6183047

Tx prefix hash: 0e2608f6d7bd2573a96e4a2e506a18380bc658f4490409c647e7ba8d1477428f
Tx public key: 385e79e8ece61a85963560f3def8bf9bab4ed5c32fcd01e802a45639ae55d08a
Timestamp: 1587143722 Timestamp [UCT]: 2020-04-17 17:15:22 Age [y:d:h:m:s]: 04:273:13:32:13
Block: 93628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104087 RingCT/type: yes/0
Extra: 01385e79e8ece61a85963560f3def8bf9bab4ed5c32fcd01e802a45639ae55d08a02110000011b45705818000000000000000000

1 output(s) for total of 300.450090656000 dcy

stealth address amount amount idx
00: 72c71e5aa57d2c6453145bf5e90796735937c985c0b0a66f13df44852348182d 300.450090656000 166680 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": 93638, "vin": [ { "gen": { "height": 93628 } } ], "vout": [ { "amount": 300450090656, "target": { "key": "72c71e5aa57d2c6453145bf5e90796735937c985c0b0a66f13df44852348182d" } } ], "extra": [ 1, 56, 94, 121, 232, 236, 230, 26, 133, 150, 53, 96, 243, 222, 248, 191, 155, 171, 78, 213, 195, 47, 205, 1, 232, 2, 164, 86, 57, 174, 85, 208, 138, 2, 17, 0, 0, 1, 27, 69, 112, 88, 24, 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