Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342cf15aab81db0b5ce76b429dde55480a168eea106326b718e3bb035977ae6e

Tx prefix hash: 1028628b0dc5d3572ddf9cde096676e2c716c9c7c5e672835f91936730f17bf0
Tx public key: 4773c83eae0fc732ea6623fc32469617d3b96d2802107979ccc1b40eb3e2a5cc
Timestamp: 1706791606 Timestamp [UCT]: 2024-02-01 12:46:46 Age [y:d:h:m:s]: 01:066:04:57:42
Block: 948037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308378 RingCT/type: yes/0
Extra: 014773c83eae0fc732ea6623fc32469617d3b96d2802107979ccc1b40eb3e2a5cc02110000000681d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a5c1a9154f3894d21dc9dd605d862ccd39d8371252f737359f6b77ed6b2ea5d 0.600000000000 1406407 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": 948047, "vin": [ { "gen": { "height": 948037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a5c1a9154f3894d21dc9dd605d862ccd39d8371252f737359f6b77ed6b2ea5d" } } ], "extra": [ 1, 71, 115, 200, 62, 174, 15, 199, 50, 234, 102, 35, 252, 50, 70, 150, 23, 211, 185, 109, 40, 2, 16, 121, 121, 204, 193, 180, 14, 179, 226, 165, 204, 2, 17, 0, 0, 0, 6, 129, 215, 29, 85, 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