Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcec01b2e79d4728a735734edced430dfcfc030b04ae89465310f17d2de011a6

Tx prefix hash: 04efd92322f59ca920ccf8a8f2699cc6bfe356d2a7e95c2c4cd9f56c38dbd6c3
Tx public key: 407fc40eb3427946412fa2bc2c5efee8dfea2ee900a6a88a323f5fd6418296db
Timestamp: 1731645839 Timestamp [UCT]: 2024-11-15 04:43:59 Age [y:d:h:m:s]: 00:126:23:55:23
Block: 1154007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90587 RingCT/type: yes/0
Extra: 01407fc40eb3427946412fa2bc2c5efee8dfea2ee900a6a88a323f5fd6418296db0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df0bbce6b3555129e021804cf434b25d8de4d1a55f0e89b0fde15c92ea890ab2 0.600000000000 1639618 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": 1154017, "vin": [ { "gen": { "height": 1154007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df0bbce6b3555129e021804cf434b25d8de4d1a55f0e89b0fde15c92ea890ab2" } } ], "extra": [ 1, 64, 127, 196, 14, 179, 66, 121, 70, 65, 47, 162, 188, 44, 94, 254, 232, 223, 234, 46, 233, 0, 166, 168, 138, 50, 63, 95, 214, 65, 130, 150, 219, 2, 17, 0, 0, 0, 3, 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