Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f73e2abaf539292d8d4ecef3c65100dc949b62b77a75df8f0ef1866ec2a55b84

Tx prefix hash: b4432ecb616ef6474eaa2a3fff0f150f3dfb7cdf3a66d854210556ec2bb45006
Tx public key: 8eb947e09244e0e595eb95e07dcd4c4c735a45ea617213203eb17c8fb621cffa
Timestamp: 1708610516 Timestamp [UCT]: 2024-02-22 14:01:56 Age [y:d:h:m:s]: 01:023:01:47:16
Block: 963133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277516 RingCT/type: yes/0
Extra: 018eb947e09244e0e595eb95e07dcd4c4c735a45ea617213203eb17c8fb621cffa0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9d7fd94b44b023fe0001fe2690492179ffb64b63d446589b199642c5cfd940e 0.600000000000 1422832 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": 963143, "vin": [ { "gen": { "height": 963133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9d7fd94b44b023fe0001fe2690492179ffb64b63d446589b199642c5cfd940e" } } ], "extra": [ 1, 142, 185, 71, 224, 146, 68, 224, 229, 149, 235, 149, 224, 125, 205, 76, 76, 115, 90, 69, 234, 97, 114, 19, 32, 62, 177, 124, 143, 182, 33, 207, 250, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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