Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa0c8a1bf8878d8d62f082bb4d5cd00ef6344f6e744d3d693717b7c962227d5d

Tx prefix hash: f8e1f48b7314647f29c990f43b9176483410e49d52570ed331f74d4fac2d5f10
Tx public key: 88c3ae8b835a2242375420f920d3a6e88750884ab53b1eccfc87f43e24161ed4
Timestamp: 1725765651 Timestamp [UCT]: 2024-09-08 03:20:51 Age [y:d:h:m:s]: 00:169:01:07:36
Block: 1105359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120613 RingCT/type: yes/0
Extra: 0188c3ae8b835a2242375420f920d3a6e88750884ab53b1eccfc87f43e24161ed402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 879036a3806c7c93e2c71b2f1b5278a30c0d65a1407af598bae47a0572694176 0.600000000000 1582700 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": 1105369, "vin": [ { "gen": { "height": 1105359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "879036a3806c7c93e2c71b2f1b5278a30c0d65a1407af598bae47a0572694176" } } ], "extra": [ 1, 136, 195, 174, 139, 131, 90, 34, 66, 55, 84, 32, 249, 32, 211, 166, 232, 135, 80, 136, 74, 181, 59, 30, 204, 252, 135, 244, 62, 36, 22, 30, 212, 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