Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ec47e18cf3817a927428f3b943d3191b4da7c6f5e1dead7fdc9bd11cbf21c4

Tx prefix hash: 06d6d4d11a6503a5bd79c5330ad57b0f0a721c4549289587c13df2a3b6efdf63
Tx public key: 0c7fdb81ae7c1aa3090f3e71108111c74b81276f774c1e70e49935924cd30e4e
Timestamp: 1725080032 Timestamp [UCT]: 2024-08-31 04:53:52 Age [y:d:h:m:s]: 00:120:11:53:21
Block: 1099672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86177 RingCT/type: yes/0
Extra: 010c7fdb81ae7c1aa3090f3e71108111c74b81276f774c1e70e49935924cd30e4e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11ccf8d6f9daf34dd525fa1b16f98a50959168ae49afa87e1fbc8b84ae375a05 0.600000000000 1575637 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": 1099682, "vin": [ { "gen": { "height": 1099672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11ccf8d6f9daf34dd525fa1b16f98a50959168ae49afa87e1fbc8b84ae375a05" } } ], "extra": [ 1, 12, 127, 219, 129, 174, 124, 26, 163, 9, 15, 62, 113, 16, 129, 17, 199, 75, 129, 39, 111, 119, 76, 30, 112, 228, 153, 53, 146, 76, 211, 14, 78, 2, 17, 0, 0, 0, 1, 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