Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19d213fbdf2f48852e680e6376e3294d0c3a284526ce5292275043edd0956c58

Tx prefix hash: 768a84032a6fce6dde502e07f364d4caaa20e616422f9b39d8727f2bb17e2d2e
Tx public key: b91e0918efa16dfe8108af34698befb4d17083c323b7fcd4212b2e0ef640fee8
Timestamp: 1736491271 Timestamp [UCT]: 2025-01-10 06:41:11 Age [y:d:h:m:s]: 00:082:02:25:54
Block: 1194141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58443 RingCT/type: yes/0
Extra: 01b91e0918efa16dfe8108af34698befb4d17083c323b7fcd4212b2e0ef640fee80211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd2f905dfe0fa1d72d499c32874c6ab28369daf16fea5cc49f741002748646c4 0.600000000000 1680708 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": 1194151, "vin": [ { "gen": { "height": 1194141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd2f905dfe0fa1d72d499c32874c6ab28369daf16fea5cc49f741002748646c4" } } ], "extra": [ 1, 185, 30, 9, 24, 239, 161, 109, 254, 129, 8, 175, 52, 105, 139, 239, 180, 209, 112, 131, 195, 35, 183, 252, 212, 33, 43, 46, 14, 246, 64, 254, 232, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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