Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 383aaf798a213080a2d41666384def4bb44380b9b8a88d8c8513a2d4452b2220

Tx prefix hash: ea1421de1408159c61e8ca524f1bc7f99ca990c53d9dc501651a9280e72d0c53
Tx public key: 53ec994602ca72133cce8aad5ca9ccfd811034e5df394e22dc3c422254d6fd8b
Timestamp: 1701123814 Timestamp [UCT]: 2023-11-27 22:23:34 Age [y:d:h:m:s]: 01:341:21:30:39
Block: 901061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503221 RingCT/type: yes/0
Extra: 0153ec994602ca72133cce8aad5ca9ccfd811034e5df394e22dc3c422254d6fd8b02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.634469633000 dcy

stealth address amount amount idx
00: f3a558376e9cd50436b3ecfbfdc6144f187c2cd16408b91bd114357ea111b138 0.634469633000 1357592 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": 901071, "vin": [ { "gen": { "height": 901061 } } ], "vout": [ { "amount": 634469633, "target": { "key": "f3a558376e9cd50436b3ecfbfdc6144f187c2cd16408b91bd114357ea111b138" } } ], "extra": [ 1, 83, 236, 153, 70, 2, 202, 114, 19, 60, 206, 138, 173, 92, 169, 204, 253, 129, 16, 52, 229, 223, 57, 78, 34, 220, 60, 66, 34, 84, 214, 253, 139, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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