Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa5d5ab52d65daf2c2842feae89438ce3d1595be5763a7422ee1766ec5143138

Tx prefix hash: f6f628b9d733ebca35c125a152db5360499cfef9d791b53271ef5d0e460cb030
Tx public key: f5f8de87b8232c09d6d4b317c604d1c4577d2c4c1b892ffa061ea2c09051f0b6
Timestamp: 1723668821 Timestamp [UCT]: 2024-08-14 20:53:41 Age [y:d:h:m:s]: 00:246:12:08:16
Block: 1087967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176068 RingCT/type: yes/0
Extra: 01f5f8de87b8232c09d6d4b317c604d1c4577d2c4c1b892ffa061ea2c09051f0b602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b70fdfe2f83ca7cd0b48df8d6308226c32cca5f326a5f53a94332570375c9f65 0.600000000000 1562578 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": 1087977, "vin": [ { "gen": { "height": 1087967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b70fdfe2f83ca7cd0b48df8d6308226c32cca5f326a5f53a94332570375c9f65" } } ], "extra": [ 1, 245, 248, 222, 135, 184, 35, 44, 9, 214, 212, 179, 23, 198, 4, 209, 196, 87, 125, 44, 76, 27, 137, 47, 250, 6, 30, 162, 192, 144, 81, 240, 182, 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