Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8cba5a13752b561431d4cb4cf9a1fe7a1dc72d7d8b2135205443bb574db5188

Tx prefix hash: 6b9a0dea23c1b0ae3fdd8a848820e945c77b5d2d2aa5ed21fbcbf8598db801bb
Tx public key: 79950c485d3354a715fcc620298f4b916129c192c81d5a6a79dd8729a41b1868
Timestamp: 1706291505 Timestamp [UCT]: 2024-01-26 17:51:45 Age [y:d:h:m:s]: 01:137:09:26:53
Block: 943876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359304 RingCT/type: yes/0
Extra: 0179950c485d3354a715fcc620298f4b916129c192c81d5a6a79dd8729a41b18680211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f45eb37779e0de90cd8b21ffa56488fef3478aa8405283cf55693a64d9ad91a 0.600000000000 1402102 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": 943886, "vin": [ { "gen": { "height": 943876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f45eb37779e0de90cd8b21ffa56488fef3478aa8405283cf55693a64d9ad91a" } } ], "extra": [ 1, 121, 149, 12, 72, 93, 51, 84, 167, 21, 252, 198, 32, 41, 143, 75, 145, 97, 41, 193, 146, 200, 29, 90, 106, 121, 221, 135, 41, 164, 27, 24, 104, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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