Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d866d8ef0f33a15d8cad7f420b545ef75eaf2460cafe4fa45e72f409b0531329

Tx prefix hash: 4f3f1b33fb2f776b5b18fa5e542b96215f15797183892006c50ef83ea7cfdd61
Tx public key: 623c3ad66f74c86e4f40800b79a64d65eacc245b17c9f52e43182c66d9128b53
Timestamp: 1734151778 Timestamp [UCT]: 2024-12-14 04:49:38 Age [y:d:h:m:s]: 00:124:21:28:55
Block: 1174783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89047 RingCT/type: yes/0
Extra: 01623c3ad66f74c86e4f40800b79a64d65eacc245b17c9f52e43182c66d9128b530211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bd920d2fc0cccfc92c5d10fb6f9ea647280e00a06f0554561be45f20acb1ed4 0.600000000000 1660978 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": 1174793, "vin": [ { "gen": { "height": 1174783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bd920d2fc0cccfc92c5d10fb6f9ea647280e00a06f0554561be45f20acb1ed4" } } ], "extra": [ 1, 98, 60, 58, 214, 111, 116, 200, 110, 79, 64, 128, 11, 121, 166, 77, 101, 234, 204, 36, 91, 23, 201, 245, 46, 67, 24, 44, 102, 217, 18, 139, 83, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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