Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0e196f52a41e4f4099a2c1a1d15bc250ff08aa6864dacac07331be409d8ba0b

Tx prefix hash: 795a5c48b2f79163fd98aac6bbadea76d6c16e142d5bb0f3a6001397d3cfdcff
Tx public key: f04f3320be29968dd4c291bf99ad919fc1084c6076fa53124a02849870329674
Timestamp: 1707210933 Timestamp [UCT]: 2024-02-06 09:15:33 Age [y:d:h:m:s]: 01:020:14:14:46
Block: 951516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275748 RingCT/type: yes/0
Extra: 01f04f3320be29968dd4c291bf99ad919fc1084c6076fa53124a02849870329674021100000003ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0418a6d03db0880c8e33331b1db01da5b56f4b311c7a2bbe4e4df6ba7ff4a286 0.600000000000 1410290 of 15

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": 951526, "vin": [ { "gen": { "height": 951516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0418a6d03db0880c8e33331b1db01da5b56f4b311c7a2bbe4e4df6ba7ff4a286" } } ], "extra": [ 1, 240, 79, 51, 32, 190, 41, 150, 141, 212, 194, 145, 191, 153, 173, 145, 159, 193, 8, 76, 96, 118, 250, 83, 18, 74, 2, 132, 152, 112, 50, 150, 116, 2, 17, 0, 0, 0, 3, 236, 87, 178, 52, 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