Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df319c9622ed8767a77bd37fed1657524c23ed4535988b60f7263e84c8451237

Tx prefix hash: 20f7f71de961ab8773291f980d1127e4da73215c0a646ad9cb6507748b5c10fd
Tx public key: a0dc4153450646d0ed0308bef8aa2295d182cb0ef8b5647a4b37d46d1abba4a2
Timestamp: 1705627867 Timestamp [UCT]: 2024-01-19 01:31:07 Age [y:d:h:m:s]: 01:105:13:32:03
Block: 938379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336560 RingCT/type: yes/0
Extra: 01a0dc4153450646d0ed0308bef8aa2295d182cb0ef8b5647a4b37d46d1abba4a202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f560b102312e501f8d934a8b29c5e6ac17f29f20be59329487c983f168393fa 0.600000000000 1396449 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": 938389, "vin": [ { "gen": { "height": 938379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f560b102312e501f8d934a8b29c5e6ac17f29f20be59329487c983f168393fa" } } ], "extra": [ 1, 160, 220, 65, 83, 69, 6, 70, 208, 237, 3, 8, 190, 248, 170, 34, 149, 209, 130, 203, 14, 248, 181, 100, 122, 75, 55, 212, 109, 26, 187, 164, 162, 2, 17, 0, 0, 0, 2, 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