Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc7e7385bedd83db635dde1bd799afb8951b4915b4e0ea98e0b948c535d1fd01

Tx prefix hash: 9fecb0781c8c07457d9e96f66dbfa9cb0cae31eded7d60d103ee8fb25f020251
Tx public key: ad2cdabfcd992dc6b4590a0b00f5df077311831967a83a0ca29db69048a27153
Timestamp: 1703441314 Timestamp [UCT]: 2023-12-24 18:08:34 Age [y:d:h:m:s]: 01:067:19:13:22
Block: 920274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309550 RingCT/type: yes/0
Extra: 01ad2cdabfcd992dc6b4590a0b00f5df077311831967a83a0ca29db69048a2715302110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a3a3d68334fc3eb7772f3321cf20f11091583e2ea439c1cf88ba73fd5c0c49d 0.600000000000 1377952 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": 920284, "vin": [ { "gen": { "height": 920274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a3a3d68334fc3eb7772f3321cf20f11091583e2ea439c1cf88ba73fd5c0c49d" } } ], "extra": [ 1, 173, 44, 218, 191, 205, 153, 45, 198, 180, 89, 10, 11, 0, 245, 223, 7, 115, 17, 131, 25, 103, 168, 58, 12, 162, 157, 182, 144, 72, 162, 113, 83, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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