Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 497affb95b125f9bb1935539607a41bc4376d4101a4d12d4d59bc22ddb265f30

Tx prefix hash: 7b871c0bc69c25990ad7d8b8dd7f942c34ff8b5182bff83c9ed8559ca91d867e
Tx public key: 3d2aa3981ead5fa6a516ca47942c55a4838f05ea8a5d4f92c56f88e005cca0ac
Timestamp: 1712809616 Timestamp [UCT]: 2024-04-11 04:26:56 Age [y:d:h:m:s]: 01:207:03:42:11
Block: 997918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406742 RingCT/type: yes/0
Extra: 013d2aa3981ead5fa6a516ca47942c55a4838f05ea8a5d4f92c56f88e005cca0ac02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b623db52de2edce13898e2466d3ac7cf4696c225d5c47e86a6977135e9bac7a 0.600000000000 1458352 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": 997928, "vin": [ { "gen": { "height": 997918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b623db52de2edce13898e2466d3ac7cf4696c225d5c47e86a6977135e9bac7a" } } ], "extra": [ 1, 61, 42, 163, 152, 30, 173, 95, 166, 165, 22, 202, 71, 148, 44, 85, 164, 131, 143, 5, 234, 138, 93, 79, 146, 197, 111, 136, 224, 5, 204, 160, 172, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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