Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80e5667303f3a8224fb04625f7d9830065e4f7aff1e73a46b1a7547da0d2c22a

Tx prefix hash: e6c08e21b2ece9bfb6210504de7bd3b832654f74530a57a416c98572a4b46f9e
Tx public key: f8b3e4088db37749e78cfe26e24553aa807a4ddaf298c494dcee5771ce4e8653
Timestamp: 1705990479 Timestamp [UCT]: 2024-01-23 06:14:39 Age [y:d:h:m:s]: 01:142:07:13:02
Block: 941372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362787 RingCT/type: yes/0
Extra: 01f8b3e4088db37749e78cfe26e24553aa807a4ddaf298c494dcee5771ce4e86530211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1854b5bd8173ba2b325ca52c311aa822b7b93bef38dedfde172dbf190b8bdf27 0.600000000000 1399518 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": 941382, "vin": [ { "gen": { "height": 941372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1854b5bd8173ba2b325ca52c311aa822b7b93bef38dedfde172dbf190b8bdf27" } } ], "extra": [ 1, 248, 179, 228, 8, 141, 179, 119, 73, 231, 140, 254, 38, 226, 69, 83, 170, 128, 122, 77, 218, 242, 152, 196, 148, 220, 238, 87, 113, 206, 78, 134, 83, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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