Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3597283ed1b953f128637eb5ae074fb131d8a06dfba82944f5cb87726103163b

Tx prefix hash: 5cb5ccca9fdd013fdfa4638f4228b1ab29f0333c73db2789fe7914e1a3e38335
Tx public key: 2c1764671b3e1f6d97166747a602f288c41d132440831665335be9f5d8064e22
Timestamp: 1577576327 Timestamp [UCT]: 2019-12-28 23:38:47 Age [y:d:h:m:s]: 05:005:04:30:15
Block: 33912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153709 RingCT/type: yes/0
Extra: 012c1764671b3e1f6d97166747a602f288c41d132440831665335be9f5d8064e22021100000096ac34bf9e000000000000000000

1 output(s) for total of 473.845022576000 dcy

stealth address amount amount idx
00: 0b6cbc3161d5d9c00c0b0bde67d8a64a168733a46c055f4f164f4f5df29e0db2 473.845022576000 56977 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": 33922, "vin": [ { "gen": { "height": 33912 } } ], "vout": [ { "amount": 473845022576, "target": { "key": "0b6cbc3161d5d9c00c0b0bde67d8a64a168733a46c055f4f164f4f5df29e0db2" } } ], "extra": [ 1, 44, 23, 100, 103, 27, 62, 31, 109, 151, 22, 103, 71, 166, 2, 242, 136, 196, 29, 19, 36, 64, 131, 22, 101, 51, 91, 233, 245, 216, 6, 78, 34, 2, 17, 0, 0, 0, 150, 172, 52, 191, 158, 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