Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b66caa43f90a4e9a8ccabeb66acc70e1766ce46d2f7965332c7e1c3c345585d3

Tx prefix hash: 0b55cffe03ab275302ca008d8b2727eb25dbfff1c5d237fe5ce8d3b2773a22bd
Tx public key: b99962a54024a3ab6d3bd8c1288d82ec249cc375292c569eea5aa415c6b30373
Timestamp: 1704433977 Timestamp [UCT]: 2024-01-05 05:52:57 Age [y:d:h:m:s]: 01:098:14:51:52
Block: 928481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331609 RingCT/type: yes/0
Extra: 01b99962a54024a3ab6d3bd8c1288d82ec249cc375292c569eea5aa415c6b3037302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04bacb5000d5bc49e129f4660ec197f695ee37bcc630e40025517b5714a0a4aa 0.600000000000 1386341 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": 928491, "vin": [ { "gen": { "height": 928481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04bacb5000d5bc49e129f4660ec197f695ee37bcc630e40025517b5714a0a4aa" } } ], "extra": [ 1, 185, 153, 98, 165, 64, 36, 163, 171, 109, 59, 216, 193, 40, 141, 130, 236, 36, 156, 195, 117, 41, 44, 86, 158, 234, 90, 164, 21, 198, 179, 3, 115, 2, 17, 0, 0, 0, 5, 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