Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df68f5b1e89f097339761f83aaf795e0f62dad7f8a39e524f36d53531b40d3f1

Tx prefix hash: f499e585a1fcbb331aba5542705339ab6afe4608e39d6f33b21983169f053810
Tx public key: 8eab91830da469c4d0f10c7601bb9ad1d9b1d55e633d59da8e7dd56929d9c48b
Timestamp: 1736726070 Timestamp [UCT]: 2025-01-12 23:54:30 Age [y:d:h:m:s]: 00:158:17:28:34
Block: 1196070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113123 RingCT/type: yes/0
Extra: 018eab91830da469c4d0f10c7601bb9ad1d9b1d55e633d59da8e7dd56929d9c48b0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6aba17e9ff199240cc4b0203d94948b5e1ae5026ff92788cd52b3ddadb7d0850 0.600000000000 1682667 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": 1196080, "vin": [ { "gen": { "height": 1196070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6aba17e9ff199240cc4b0203d94948b5e1ae5026ff92788cd52b3ddadb7d0850" } } ], "extra": [ 1, 142, 171, 145, 131, 13, 164, 105, 196, 208, 241, 12, 118, 1, 187, 154, 209, 217, 177, 213, 94, 99, 61, 89, 218, 142, 125, 213, 105, 41, 217, 196, 139, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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