Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f68ea4eaa180cf1a4b828f47c51759b5560c91234d22e7dfb0b23fca69100a4e

Tx prefix hash: 8949b6ce3bbe8078ccead2ce5cb751ca89d5878c2c73d43bc28cf462ef8b9e1a
Tx public key: ce58232dba764579c09e40dc2e6fe1740038abfe8f7e90ae2a8f8068a0164f69
Timestamp: 1723765654 Timestamp [UCT]: 2024-08-15 23:47:34 Age [y:d:h:m:s]: 00:235:22:40:18
Block: 1088777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168497 RingCT/type: yes/0
Extra: 01ce58232dba764579c09e40dc2e6fe1740038abfe8f7e90ae2a8f8068a0164f69021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54a2a529f4fe1494c03d80fdda5d5fb201cec572a430583a8dda1831d3a13fd0 0.600000000000 1563396 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": 1088787, "vin": [ { "gen": { "height": 1088777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54a2a529f4fe1494c03d80fdda5d5fb201cec572a430583a8dda1831d3a13fd0" } } ], "extra": [ 1, 206, 88, 35, 45, 186, 118, 69, 121, 192, 158, 64, 220, 46, 111, 225, 116, 0, 56, 171, 254, 143, 126, 144, 174, 42, 143, 128, 104, 160, 22, 79, 105, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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