Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebb354fb115b221293afe9bbd055ee72fdb0be6abc48a4fc62fdd1a5a10f2de9

Tx prefix hash: 5ca44c109dcf0a62900ad3205f0335fbea3f086522a736c3d81eb5f3a66cbe50
Tx public key: 3dafe595415be6b5f43501168663e4aa0d7d41b1372d0940b5abb7ddd72940cf
Timestamp: 1727890931 Timestamp [UCT]: 2024-10-02 17:42:11 Age [y:d:h:m:s]: 01:038:01:31:57
Block: 1122989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285579 RingCT/type: yes/0
Extra: 013dafe595415be6b5f43501168663e4aa0d7d41b1372d0940b5abb7ddd72940cf02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfa54cb3c9ffecb9b400a6f6c1bbcdc5400b7875965db6d873efd0e4371e75b8 0.600000000000 1605522 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": 1122999, "vin": [ { "gen": { "height": 1122989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfa54cb3c9ffecb9b400a6f6c1bbcdc5400b7875965db6d873efd0e4371e75b8" } } ], "extra": [ 1, 61, 175, 229, 149, 65, 91, 230, 181, 244, 53, 1, 22, 134, 99, 228, 170, 13, 125, 65, 177, 55, 45, 9, 64, 181, 171, 183, 221, 215, 41, 64, 207, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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