Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76967c8d7e01c9f508ef9027bf10b14b7a256c30a5686296dd3e703f8dd7ebcc

Tx prefix hash: aff606cbb7dd99f667d04bb4f9577c5220fcf1c35f5c6b93914bd31a6cc974f8
Tx public key: 084dc20f222ab27df0de227a5fa96b4c53ce461f2b1c83a1f539d4b022d5b7a0
Timestamp: 1714306030 Timestamp [UCT]: 2024-04-28 12:07:10 Age [y:d:h:m:s]: 01:026:15:51:32
Block: 1010346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280013 RingCT/type: yes/0
Extra: 01084dc20f222ab27df0de227a5fa96b4c53ce461f2b1c83a1f539d4b022d5b7a002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bea1d234795f27204d7c4f27d82832c08113d0a4a554a1d5cb5b6baf9b756487 0.600000000000 1472272 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": 1010356, "vin": [ { "gen": { "height": 1010346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bea1d234795f27204d7c4f27d82832c08113d0a4a554a1d5cb5b6baf9b756487" } } ], "extra": [ 1, 8, 77, 194, 15, 34, 42, 178, 125, 240, 222, 34, 122, 95, 169, 107, 76, 83, 206, 70, 31, 43, 28, 131, 161, 245, 57, 212, 176, 34, 213, 183, 160, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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