Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faa61ea6a2d313df432a9694afae1f5f9fcc2953543734a3ca559bb8cfff88e6

Tx prefix hash: 69f659df791cbe35f15ef60b650eed074057a9fd220b9831b20aa4c10048f64c
Tx public key: cc9a4598e78d44b5ac35d94d0841ba6f531d8d7fc591e407af53cb4972087c78
Timestamp: 1704054030 Timestamp [UCT]: 2023-12-31 20:20:30 Age [y:d:h:m:s]: 01:314:01:44:45
Block: 925348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483309 RingCT/type: yes/0
Extra: 01cc9a4598e78d44b5ac35d94d0841ba6f531d8d7fc591e407af53cb4972087c78021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39c9d24666179b5efcaca4ca3c16d9599c3c4c6c890a3c5fe70087ebb4863387 0.600000000000 1383110 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": 925358, "vin": [ { "gen": { "height": 925348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39c9d24666179b5efcaca4ca3c16d9599c3c4c6c890a3c5fe70087ebb4863387" } } ], "extra": [ 1, 204, 154, 69, 152, 231, 141, 68, 181, 172, 53, 217, 77, 8, 65, 186, 111, 83, 29, 141, 127, 197, 145, 228, 7, 175, 83, 203, 73, 114, 8, 124, 120, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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