Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48ea2ec3b998a0da30ffd95da7e975f3053cfab5fb735e9ba63fb58fad740fb1

Tx prefix hash: bb525e678527bac025a041cfe9b66dcfb899ffda2491f9b37a544620a027ad9c
Tx public key: 86b5fd29b0ca60e36fa8d0246e28ea116c7d30eb8c5c1d541cae9a894138d4c3
Timestamp: 1577114770 Timestamp [UCT]: 2019-12-23 15:26:10 Age [y:d:h:m:s]: 05:137:10:21:33
Block: 30018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1248108 RingCT/type: yes/0
Extra: 0186b5fd29b0ca60e36fa8d0246e28ea116c7d30eb8c5c1d541cae9a894138d4c3021100000009ad433a0b000000000000000000

1 output(s) for total of 488.133672439000 dcy

stealth address amount amount idx
00: 40e92a59efa34762ede0fb0aeb3814c7ca31770290a419dff30116c116f0eca7 488.133672439000 49546 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": 30028, "vin": [ { "gen": { "height": 30018 } } ], "vout": [ { "amount": 488133672439, "target": { "key": "40e92a59efa34762ede0fb0aeb3814c7ca31770290a419dff30116c116f0eca7" } } ], "extra": [ 1, 134, 181, 253, 41, 176, 202, 96, 227, 111, 168, 208, 36, 110, 40, 234, 17, 108, 125, 48, 235, 140, 92, 29, 84, 28, 174, 154, 137, 65, 56, 212, 195, 2, 17, 0, 0, 0, 9, 173, 67, 58, 11, 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