Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85396c39a053c9cfc863f7d32b2fe126fd09a71afd3ac2bae9038d44b10abb08

Tx prefix hash: 1935b5f16296b6274a1a3d591e95b1466796615d6cf2e7d65cf22af1a5498f85
Tx public key: ebd568b4f80c4583fa082573cdc5fb118a4dfc841d47de9885a326749b85bbf5
Timestamp: 1714090612 Timestamp [UCT]: 2024-04-26 00:16:52 Age [y:d:h:m:s]: 00:258:14:09:31
Block: 1008552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185103 RingCT/type: yes/0
Extra: 01ebd568b4f80c4583fa082573cdc5fb118a4dfc841d47de9885a326749b85bbf502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c43f29c317ed3d8f4d35612b42aadb44446e12a5a6a5cbf1b24350b9d0b20022 0.600000000000 1470024 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": 1008562, "vin": [ { "gen": { "height": 1008552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c43f29c317ed3d8f4d35612b42aadb44446e12a5a6a5cbf1b24350b9d0b20022" } } ], "extra": [ 1, 235, 213, 104, 180, 248, 12, 69, 131, 250, 8, 37, 115, 205, 197, 251, 17, 138, 77, 252, 132, 29, 71, 222, 152, 133, 163, 38, 116, 155, 133, 187, 245, 2, 17, 0, 0, 0, 3, 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