Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1bc5233d1d63c869d160e4c090fa02d7279a50d73920f9f0162e7f552888c90

Tx prefix hash: 1fe943e0769ab706f7212aab71491bdd9b8d4135cc8dafffeeb3f982d7364418
Tx public key: ce4a46a1d15f1ed01f073d49a2dab3096cd33e101c6ec67a0b0423bd4c995b97
Timestamp: 1579231224 Timestamp [UCT]: 2020-01-17 03:20:24 Age [y:d:h:m:s]: 05:293:11:30:19
Block: 47195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1357660 RingCT/type: yes/0
Extra: 01ce4a46a1d15f1ed01f073d49a2dab3096cd33e101c6ec67a0b0423bd4c995b97021100000001b221b3d1000000000000000000

1 output(s) for total of 428.177863206000 dcy

stealth address amount amount idx
00: 532a6c1696ebeaceb1973630034abbcfa5ebc93f5a7f6ab1f644c56fe98be094 428.177863206000 87205 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": 47205, "vin": [ { "gen": { "height": 47195 } } ], "vout": [ { "amount": 428177863206, "target": { "key": "532a6c1696ebeaceb1973630034abbcfa5ebc93f5a7f6ab1f644c56fe98be094" } } ], "extra": [ 1, 206, 74, 70, 161, 209, 95, 30, 208, 31, 7, 61, 73, 162, 218, 179, 9, 108, 211, 62, 16, 28, 110, 198, 122, 11, 4, 35, 189, 76, 153, 91, 151, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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