Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60a458e115f853c80427ab772b382aed9ed38585529dac429738a09e5af4756f

Tx prefix hash: f9cacdd4620ec8de43be728db8b14d5672bfd8b441def8569e91d153661a54a4
Tx public key: 22a91c93e19bf5abb5bc42a24e89832c4009a20f54c1f5f87ee193a9e3da73b7
Timestamp: 1726697126 Timestamp [UCT]: 2024-09-18 22:05:26 Age [y:d:h:m:s]: 00:204:00:59:09
Block: 1113075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145651 RingCT/type: yes/0
Extra: 0122a91c93e19bf5abb5bc42a24e89832c4009a20f54c1f5f87ee193a9e3da73b702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc44e192f539466718a0e70d53c2604531bbd6d580c6ee0aa7ed725874f57e7c 0.600000000000 1592618 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": 1113085, "vin": [ { "gen": { "height": 1113075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc44e192f539466718a0e70d53c2604531bbd6d580c6ee0aa7ed725874f57e7c" } } ], "extra": [ 1, 34, 169, 28, 147, 225, 155, 245, 171, 181, 188, 66, 162, 78, 137, 131, 44, 64, 9, 162, 15, 84, 193, 245, 248, 126, 225, 147, 169, 227, 218, 115, 183, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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