Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c00347340a41c3ca551ca4ee1ecc5321861c36672c6fddfb72d25c20c65769e

Tx prefix hash: 050e8289a2758dd89c9e0cd6024555cd4153e16e08364d4a657b8d4b265e50ba
Tx public key: e4fd079d4b4c45fce5361402480b2756b59c1d4452183ac6153eaaefd33cdca8
Timestamp: 1577116938 Timestamp [UCT]: 2019-12-23 16:02:18 Age [y:d:h:m:s]: 05:313:05:52:19
Block: 30029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1371468 RingCT/type: yes/0
Extra: 01e4fd079d4b4c45fce5361402480b2756b59c1d4452183ac6153eaaefd33cdca80211000000194ac5aa02000000000000000000

1 output(s) for total of 488.092708194000 dcy

stealth address amount amount idx
00: 94c6fd1a7f13f27e1fb026c6b0d4864ed2e8823e8af560bbe84ee3d6fc96c3e2 488.092708194000 49567 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": 30039, "vin": [ { "gen": { "height": 30029 } } ], "vout": [ { "amount": 488092708194, "target": { "key": "94c6fd1a7f13f27e1fb026c6b0d4864ed2e8823e8af560bbe84ee3d6fc96c3e2" } } ], "extra": [ 1, 228, 253, 7, 157, 75, 76, 69, 252, 229, 54, 20, 2, 72, 11, 39, 86, 181, 156, 29, 68, 82, 24, 58, 198, 21, 62, 170, 239, 211, 60, 220, 168, 2, 17, 0, 0, 0, 25, 74, 197, 170, 2, 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