Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdb65fe41b0bd3bb25722f1f344dd791acc0ffa040b56e756f4434c058b20fc0

Tx prefix hash: c1eb53d495da7cffb88be4eab88ae92468c2611ce33ceeb376e18a6238b4bffe
Tx public key: c7ec9b2f6d3e7c67fe74523dc0a088df4f8471ddf8c5f12f84d3aa7af59fe4bc
Timestamp: 1734702456 Timestamp [UCT]: 2024-12-20 13:47:36 Age [y:d:h:m:s]: 00:094:20:04:04
Block: 1179361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67531 RingCT/type: yes/0
Extra: 01c7ec9b2f6d3e7c67fe74523dc0a088df4f8471ddf8c5f12f84d3aa7af59fe4bc0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63d049e5d38ba48ee9327b76948c8367849ae70d5976c1e9c8b48be92a0e3484 0.600000000000 1665756 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": 1179371, "vin": [ { "gen": { "height": 1179361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63d049e5d38ba48ee9327b76948c8367849ae70d5976c1e9c8b48be92a0e3484" } } ], "extra": [ 1, 199, 236, 155, 47, 109, 62, 124, 103, 254, 116, 82, 61, 192, 160, 136, 223, 79, 132, 113, 221, 248, 197, 241, 47, 132, 211, 170, 122, 245, 159, 228, 188, 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