Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfe0b2fadb16ecae3313a1829f58b456e9bb6046ba48d15591dc13fde5dbcb65

Tx prefix hash: 07693f32931bcf97282824558277584a266e6ad9babcab572f5477b7cb6ccbe6
Tx public key: 6a483272f700fb64b51b8b0736f9137e6710a7255ebdaf2b59a2d6b3efcaa7f8
Timestamp: 1719028854 Timestamp [UCT]: 2024-06-22 04:00:54 Age [y:d:h:m:s]: 00:272:13:14:50
Block: 1049491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194768 RingCT/type: yes/0
Extra: 016a483272f700fb64b51b8b0736f9137e6710a7255ebdaf2b59a2d6b3efcaa7f80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5579bcbfcf755f8eae82bd7b503d54c7183347328a059f31b5068ab0b13fe4b8 0.600000000000 1519590 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": 1049501, "vin": [ { "gen": { "height": 1049491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5579bcbfcf755f8eae82bd7b503d54c7183347328a059f31b5068ab0b13fe4b8" } } ], "extra": [ 1, 106, 72, 50, 114, 247, 0, 251, 100, 181, 27, 139, 7, 54, 249, 19, 126, 103, 16, 167, 37, 94, 189, 175, 43, 89, 162, 214, 179, 239, 202, 167, 248, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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