Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac0eaa00496368ca6498c8b4b5f4458265eddb03aa08705c11706bf1e53518f7

Tx prefix hash: 5b66f8555d338d3c42707c94f27df4e758bef0de4457e46cd0521a40fd506a13
Tx public key: 798150853fde02fe0dfd22a2d593a8417ab14d34fb5acb3ba9b98e1d106bff53
Timestamp: 1714432750 Timestamp [UCT]: 2024-04-29 23:19:10 Age [y:d:h:m:s]: 00:338:00:22:36
Block: 1011386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241631 RingCT/type: yes/0
Extra: 01798150853fde02fe0dfd22a2d593a8417ab14d34fb5acb3ba9b98e1d106bff530211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54670e3d086cc8600b150bc6bcf164b8c6500e96e8f7b27f02372d775e8333cb 0.600000000000 1473604 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": 1011396, "vin": [ { "gen": { "height": 1011386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54670e3d086cc8600b150bc6bcf164b8c6500e96e8f7b27f02372d775e8333cb" } } ], "extra": [ 1, 121, 129, 80, 133, 63, 222, 2, 254, 13, 253, 34, 162, 213, 147, 168, 65, 122, 177, 77, 52, 251, 90, 203, 59, 169, 185, 142, 29, 16, 107, 255, 83, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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