Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29cef941cab77621675c42cde7c7bda9f79aa6d81c80765284c4ff4f01cf1731

Tx prefix hash: cc953297d9636df219d11024ad8edb93914e3f680df54531cb7c60fe7a4e4cc2
Tx public key: 0aa8d77905723ded4eaa1a567cec543a12d57f56c6d4bc5706b6fcbffe857fb0
Timestamp: 1728830621 Timestamp [UCT]: 2024-10-13 14:43:41 Age [y:d:h:m:s]: 00:160:19:00:51
Block: 1130769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114692 RingCT/type: yes/0
Extra: 010aa8d77905723ded4eaa1a567cec543a12d57f56c6d4bc5706b6fcbffe857fb002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a3f205916c1acd7443985d6a6d5798d5b4eedf944c5a04bd677b80438743c1c 0.600000000000 1613648 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": 1130779, "vin": [ { "gen": { "height": 1130769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a3f205916c1acd7443985d6a6d5798d5b4eedf944c5a04bd677b80438743c1c" } } ], "extra": [ 1, 10, 168, 215, 121, 5, 114, 61, 237, 78, 170, 26, 86, 124, 236, 84, 58, 18, 213, 127, 86, 198, 212, 188, 87, 6, 182, 252, 191, 254, 133, 127, 176, 2, 17, 0, 0, 0, 2, 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