Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84b3262dbfe6eeb1907e3d085f8055f2c86fdefdee8507bdea89a656c7f8634b

Tx prefix hash: de17d5557a216df6ebed2181360da0684b4a88397070d46e456649a348d4f77c
Tx public key: c3dca4eb59e5df14434c2a173c007c1c7f26ddc9e636a0ba0ef1cb86dce2b790
Timestamp: 1585551239 Timestamp [UCT]: 2020-03-30 06:53:59 Age [y:d:h:m:s]: 04:277:18:29:36
Block: 89934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097600 RingCT/type: yes/0
Extra: 01c3dca4eb59e5df14434c2a173c007c1c7f26ddc9e636a0ba0ef1cb86dce2b79002110000000dd81c26c0000000000000000000

1 output(s) for total of 309.038153339000 dcy

stealth address amount amount idx
00: bf0b8b8453da46e02d1826f5376bb694ee6ea11746e0b00c6cf582fa8e23d252 309.038153339000 161158 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": 89944, "vin": [ { "gen": { "height": 89934 } } ], "vout": [ { "amount": 309038153339, "target": { "key": "bf0b8b8453da46e02d1826f5376bb694ee6ea11746e0b00c6cf582fa8e23d252" } } ], "extra": [ 1, 195, 220, 164, 235, 89, 229, 223, 20, 67, 76, 42, 23, 60, 0, 124, 28, 127, 38, 221, 201, 230, 54, 160, 186, 14, 241, 203, 134, 220, 226, 183, 144, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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