Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83dcdeba6c9c40c07d656e58b039b8f7595cc03f5ccc4df42d2f544e35bbcfa2

Tx prefix hash: 0d131e0787b09e2bfd725063f4b5643536f886867ce7bacb537beac70c23a055
Tx public key: 865ab1a0e5cf01834ad71bd075c5f0b9cdbcc91de69c2b53b39c2068d13ba2db
Timestamp: 1728414031 Timestamp [UCT]: 2024-10-08 19:00:31 Age [y:d:h:m:s]: 01:032:22:22:01
Block: 1127312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281910 RingCT/type: yes/0
Extra: 01865ab1a0e5cf01834ad71bd075c5f0b9cdbcc91de69c2b53b39c2068d13ba2db02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3023e8242aa4648c5fec60a849ac9a6cddd6d6c36f49999a2a97425a2a04dd78 0.600000000000 1610115 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": 1127322, "vin": [ { "gen": { "height": 1127312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3023e8242aa4648c5fec60a849ac9a6cddd6d6c36f49999a2a97425a2a04dd78" } } ], "extra": [ 1, 134, 90, 177, 160, 229, 207, 1, 131, 74, 215, 27, 208, 117, 197, 240, 185, 205, 188, 201, 29, 230, 156, 43, 83, 179, 156, 32, 104, 209, 59, 162, 219, 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