Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79fc88d0777d0bb379bad830a4e5fdc1b914f3dcb9dbf1bfd22a277067b19072

Tx prefix hash: 642569319f0bda6cce32f3072f860368a6a9ec9f66c9899717f11d1e5e8cdc0e
Tx public key: 45beecf183696a1c3f09a04762abddb7240ce603a4980a0c5c52152cc854063c
Timestamp: 1675491789 Timestamp [UCT]: 2023-02-04 06:23:09 Age [y:d:h:m:s]: 02:099:05:52:01
Block: 689442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592571 RingCT/type: yes/0
Extra: 0145beecf183696a1c3f09a04762abddb7240ce603a4980a0c5c52152cc854063c0211000000065029cbac000000000000000000

1 output(s) for total of 3.188543761000 dcy

stealth address amount amount idx
00: a4cf6834da4d7da5e5bcaddf4d49f8e2ff88914a51acfeebcd4a08611b3723a4 3.188543761000 1132118 of 0

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": 689452, "vin": [ { "gen": { "height": 689442 } } ], "vout": [ { "amount": 3188543761, "target": { "key": "a4cf6834da4d7da5e5bcaddf4d49f8e2ff88914a51acfeebcd4a08611b3723a4" } } ], "extra": [ 1, 69, 190, 236, 241, 131, 105, 106, 28, 63, 9, 160, 71, 98, 171, 221, 183, 36, 12, 230, 3, 164, 152, 10, 12, 92, 82, 21, 44, 200, 84, 6, 60, 2, 17, 0, 0, 0, 6, 80, 41, 203, 172, 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