Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8773f3f4e4faa20d90ea2ce03bbca3411b074025416b697dc3e953272fbe1e3f

Tx prefix hash: 7ddd5e2c90c49b98d2a56e351af7a772523f2a5855e6517f86c6f9a2984e3580
Tx public key: 80397ebc1c4eb7939a656928d966834beae8a1852e37b256ee029044463548b9
Timestamp: 1702454028 Timestamp [UCT]: 2023-12-13 07:53:48 Age [y:d:h:m:s]: 02:005:00:20:39
Block: 912111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523324 RingCT/type: yes/0
Extra: 0180397ebc1c4eb7939a656928d966834beae8a1852e37b256ee029044463548b902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b46b7c3338b38f1536fc8e00d62d3ef8b25d26ef35c0a5d480d6fb8657b5bf67 0.600000000000 1369331 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": 912121, "vin": [ { "gen": { "height": 912111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b46b7c3338b38f1536fc8e00d62d3ef8b25d26ef35c0a5d480d6fb8657b5bf67" } } ], "extra": [ 1, 128, 57, 126, 188, 28, 78, 183, 147, 154, 101, 105, 40, 217, 102, 131, 75, 234, 232, 161, 133, 46, 55, 178, 86, 238, 2, 144, 68, 70, 53, 72, 185, 2, 17, 0, 0, 0, 1, 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