Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25d094e08dd8e936380b032cc78af6badbd34a565f3e1d57e802a3987865811d

Tx prefix hash: 0887b1df5bfac7c2d23ab28fb99f6ddb5a8f60051ec31794e13a89141088b21d
Tx public key: f032bfdaa7e54df2063264923feac76f34cbf77f1f3df0747fb8c22a4c7c0c0c
Timestamp: 1721477858 Timestamp [UCT]: 2024-07-20 12:17:38 Age [y:d:h:m:s]: 00:127:04:01:49
Block: 1069808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90993 RingCT/type: yes/0
Extra: 01f032bfdaa7e54df2063264923feac76f34cbf77f1f3df0747fb8c22a4c7c0c0c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7169ce05e984e938b0d4c2a6eacfc2650abc5ebb22c7d25c67b7e56edf242f5e 0.600000000000 1541385 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": 1069818, "vin": [ { "gen": { "height": 1069808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7169ce05e984e938b0d4c2a6eacfc2650abc5ebb22c7d25c67b7e56edf242f5e" } } ], "extra": [ 1, 240, 50, 191, 218, 167, 229, 77, 242, 6, 50, 100, 146, 63, 234, 199, 111, 52, 203, 247, 127, 31, 61, 240, 116, 127, 184, 194, 42, 76, 124, 12, 12, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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