Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d50f6d6ecedbe1fd2242aee1c83d90e09854f44100df3e304d9e46c2ba294c34

Tx prefix hash: 65656634c62a771ee582e2757723df2f6d767e8c9c0b40b12c96de0140cabe95
Tx public key: f869d3cf76f873ea2f94dc8d70004d1a71c0d6a684c54033b5b6450301667d04
Timestamp: 1738898628 Timestamp [UCT]: 2025-02-07 03:23:48 Age [y:d:h:m:s]: 00:287:07:06:17
Block: 1213810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203077 RingCT/type: yes/0
Extra: 01f869d3cf76f873ea2f94dc8d70004d1a71c0d6a684c54033b5b6450301667d04021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 562e8d5cfa221a690da139f9210d3b395c94850c69b20316a5a163856cf38086 0.600000000000 1700591 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": 1213820, "vin": [ { "gen": { "height": 1213810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "562e8d5cfa221a690da139f9210d3b395c94850c69b20316a5a163856cf38086" } } ], "extra": [ 1, 248, 105, 211, 207, 118, 248, 115, 234, 47, 148, 220, 141, 112, 0, 77, 26, 113, 192, 214, 166, 132, 197, 64, 51, 181, 182, 69, 3, 1, 102, 125, 4, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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