Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a4e831a43eb023813d9aeff8d839927f5c11250bafbae5bd056a8c5204b45ff

Tx prefix hash: 739c0361f3fe19913d8714a86a424719ee5230ac3f6c9fedfb7e64a8af27d218
Tx public key: ff6633b29ea727ea39e81e86019787007a1a3ae2b7fb7cf4fe66c27b77a37cf4
Timestamp: 1740214171 Timestamp [UCT]: 2025-02-22 08:49:31 Age [y:d:h:m:s]: 00:184:11:35:07
Block: 1224664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129693 RingCT/type: yes/0
Extra: 01ff6633b29ea727ea39e81e86019787007a1a3ae2b7fb7cf4fe66c27b77a37cf4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a69ff6c005fac145a33f892a81071c0d59594c3730e459789386a675c17250b8 0.600000000000 1711527 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": 1224674, "vin": [ { "gen": { "height": 1224664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a69ff6c005fac145a33f892a81071c0d59594c3730e459789386a675c17250b8" } } ], "extra": [ 1, 255, 102, 51, 178, 158, 167, 39, 234, 57, 232, 30, 134, 1, 151, 135, 0, 122, 26, 58, 226, 183, 251, 124, 244, 254, 102, 194, 123, 119, 163, 124, 244, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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