Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e2f7f4f83bb4228dfad218d8866ed6e3203b456a049dd6c98c677babe159331

Tx prefix hash: b2b67b8561bd39922de351ef2be00924752a349b013d6272af225ce858615f4c
Tx public key: b546ec587a6b2b2b9838c210dcb9e6e93b9ae916b5b344c90f4ce320acad6bae
Timestamp: 1729250591 Timestamp [UCT]: 2024-10-18 11:23:11 Age [y:d:h:m:s]: 00:166:13:05:10
Block: 1134254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118780 RingCT/type: yes/0
Extra: 01b546ec587a6b2b2b9838c210dcb9e6e93b9ae916b5b344c90f4ce320acad6bae0211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7de6776e1a6900db369900c1e5266d3f45cab6f17b26067295ed01fc5a3e98f4 0.600000000000 1617531 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": 1134264, "vin": [ { "gen": { "height": 1134254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7de6776e1a6900db369900c1e5266d3f45cab6f17b26067295ed01fc5a3e98f4" } } ], "extra": [ 1, 181, 70, 236, 88, 122, 107, 43, 43, 152, 56, 194, 16, 220, 185, 230, 233, 59, 154, 233, 22, 181, 179, 68, 201, 15, 76, 227, 32, 172, 173, 107, 174, 2, 17, 0, 0, 0, 3, 60, 208, 252, 6, 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