Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705e67c6587116d8c6018e27712b6736c78af2a790bf1080807b1a9407eb399c

Tx prefix hash: 98972bf48e2931eff5f417157ef316f7c8b1d99235d17cb7112c54092d6569f1
Tx public key: 5b91f0e7530e922b4ff4eb1d1723a95da593cf41e571e4eea3622754fb355ddf
Timestamp: 1726618458 Timestamp [UCT]: 2024-09-18 00:14:18 Age [y:d:h:m:s]: 00:126:18:57:29
Block: 1112421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90628 RingCT/type: yes/0
Extra: 015b91f0e7530e922b4ff4eb1d1723a95da593cf41e571e4eea3622754fb355ddf02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34e41bc5df7ad0560e612f521012f0d38372ea4c7b9f0b80aa6e8427de8034db 0.600000000000 1591738 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": 1112431, "vin": [ { "gen": { "height": 1112421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34e41bc5df7ad0560e612f521012f0d38372ea4c7b9f0b80aa6e8427de8034db" } } ], "extra": [ 1, 91, 145, 240, 231, 83, 14, 146, 43, 79, 244, 235, 29, 23, 35, 169, 93, 165, 147, 207, 65, 229, 113, 228, 238, 163, 98, 39, 84, 251, 53, 93, 223, 2, 17, 0, 0, 0, 8, 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