Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0f5c4ea76b9f624cbda5d14b847cd384710d04d4aea16acadd7f7a15e1338d7

Tx prefix hash: 484ebe4712ccbe9b5d53434d977d049bcaf47b5efbaaee196f35f3952a987be3
Tx public key: 79c044b4dcbbe2e51f0f44c6fb0b389f93498fb3cb18cb272f01331dfaebbf86
Timestamp: 1671517416 Timestamp [UCT]: 2022-12-20 06:23:36 Age [y:d:h:m:s]: 02:096:17:36:50
Block: 656490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590817 RingCT/type: yes/0
Extra: 0179c044b4dcbbe2e51f0f44c6fb0b389f93498fb3cb18cb272f01331dfaebbf8602110000000475e3f0e9000000000000000000

1 output(s) for total of 4.099926632000 dcy

stealth address amount amount idx
00: a0dfc586e1f30aaea110ddd11749fd6edd30d007943f8394e290264d98e473d2 4.099926632000 1097097 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": 656500, "vin": [ { "gen": { "height": 656490 } } ], "vout": [ { "amount": 4099926632, "target": { "key": "a0dfc586e1f30aaea110ddd11749fd6edd30d007943f8394e290264d98e473d2" } } ], "extra": [ 1, 121, 192, 68, 180, 220, 187, 226, 229, 31, 15, 68, 198, 251, 11, 56, 159, 147, 73, 143, 179, 203, 24, 203, 39, 47, 1, 51, 29, 250, 235, 191, 134, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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