Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce06b12dc7249032bed4ecf467b7dd399b78745dfb35992f72ddf2b5aecbd32

Tx prefix hash: 78bbb7175e9d2fc32672e57c7295360dae196d3039c659b47dfdce97055f4d14
Tx public key: 8d38a5b90177baf2402e1ed8ea81a25a750e4f3a4da7690455d96364592bc7c3
Timestamp: 1726039761 Timestamp [UCT]: 2024-09-11 07:29:21 Age [y:d:h:m:s]: 00:210:19:08:03
Block: 1107628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150498 RingCT/type: yes/0
Extra: 018d38a5b90177baf2402e1ed8ea81a25a750e4f3a4da7690455d96364592bc7c302110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d875cc50dae54331f1616d30b4a12237ccaa7c68c5cc72c69e482eeec4d6f2c 0.600000000000 1585241 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": 1107638, "vin": [ { "gen": { "height": 1107628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d875cc50dae54331f1616d30b4a12237ccaa7c68c5cc72c69e482eeec4d6f2c" } } ], "extra": [ 1, 141, 56, 165, 185, 1, 119, 186, 242, 64, 46, 30, 216, 234, 129, 162, 90, 117, 14, 79, 58, 77, 167, 105, 4, 85, 217, 99, 100, 89, 43, 199, 195, 2, 17, 0, 0, 0, 10, 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