Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4fd98adc35e5971bcc1a5e895d10b859fe5824b8f78f13efaa1dcbed6f7e958

Tx prefix hash: 8264e3d98560d2f530f02d0664f572018543abaf4c3181b2fb5b07499c83f986
Tx public key: e36ae651236bf688e34974943bfbe9734ee1b78be3c0426e61a8973eac8dd2f5
Timestamp: 1734901225 Timestamp [UCT]: 2024-12-22 21:00:25 Age [y:d:h:m:s]: 00:320:16:43:05
Block: 1181008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226674 RingCT/type: yes/0
Extra: 01e36ae651236bf688e34974943bfbe9734ee1b78be3c0426e61a8973eac8dd2f502110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4d3b31764f10037a8915397417bce615b29c993a88b2cefc0b1eaa6933bdaa0 0.600000000000 1667423 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": 1181018, "vin": [ { "gen": { "height": 1181008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4d3b31764f10037a8915397417bce615b29c993a88b2cefc0b1eaa6933bdaa0" } } ], "extra": [ 1, 227, 106, 230, 81, 35, 107, 246, 136, 227, 73, 116, 148, 59, 251, 233, 115, 78, 225, 183, 139, 227, 192, 66, 110, 97, 168, 151, 62, 172, 141, 210, 245, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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