Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 042f0242da30a33718c8ac2372657869b15a9150c7d2d1ae3eb7f6e5001e89b5

Tx prefix hash: 7ffb0f30a7c3037d2265990abb3893d6840923150b58f51beb46c492b74a7f4d
Tx public key: 1de01c7b2fe352b7f01a22860250737dd31306c062eab413fdf22979e973ee1a
Timestamp: 1717425023 Timestamp [UCT]: 2024-06-03 14:30:23 Age [y:d:h:m:s]: 00:305:02:20:16
Block: 1036220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218034 RingCT/type: yes/0
Extra: 011de01c7b2fe352b7f01a22860250737dd31306c062eab413fdf22979e973ee1a02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aef7ff0c3b13ba515bce3cc51cd8842c0f06ce74d2d308e6c2a2ff57181d2d9 0.600000000000 1504745 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": 1036230, "vin": [ { "gen": { "height": 1036220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aef7ff0c3b13ba515bce3cc51cd8842c0f06ce74d2d308e6c2a2ff57181d2d9" } } ], "extra": [ 1, 29, 224, 28, 123, 47, 227, 82, 183, 240, 26, 34, 134, 2, 80, 115, 125, 211, 19, 6, 192, 98, 234, 180, 19, 253, 242, 41, 121, 233, 115, 238, 26, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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